Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

fix(deps): update dependency @graphql-tools/utils to v9 #130

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-tools/utils 7.2.3 -> 9.2.1 age adoption passing confidence

Release Notes

ardatan/graphql-tools

v9.2.1

Compare Source

Patch Changes
  • b5c8f640 Thanks @​ardatan! - Do not use a global WeakMap for memoize2of4, and introduce memoize2of5

v9.2.0

Compare Source

Minor Changes
Patch Changes

v9.1.4

Compare Source

Patch Changes

v9.1.3

Compare Source

Patch Changes

v9.1.2

Compare Source

Patch Changes

v9.1.1

Compare Source

Patch Changes

v9.1.0

Compare Source

Minor Changes

v9.0.1

Compare Source

Patch Changes

v9.0.0

Compare Source

Major Changes
  • #​4801 8f6d3efc Thanks @​ardatan! - BREAKING: checkValidationErrors has been dropped and validateGraphQlDocuments now accepts DocumentNode[] instead and it throws the original GraphQLErrors with the correct stack trace

  • #​4796 80836fa7 Thanks @​saihaj! - update collectFields to support collecting deffered values

Minor Changes

v8.13.1

Compare Source

Patch Changes

v8.13.0

Compare Source

Minor Changes
Patch Changes

v8.12.0

Compare Source

Minor Changes

v8.11.0

Compare Source

Minor Changes
Patch Changes

v8.10.1

Compare Source

Patch Changes

v8.10.0

Compare Source

Minor Changes

v8.9.1

Compare Source

Patch Changes

v8.9.0

Compare Source

Minor Changes

v8.8.0

Compare Source

Minor Changes
  • d76a299: Support TypeScript module resolution.
Patch Changes
  • a0abbbc: fix(visitResult): handle introspection fields correctly with an introspection query result

v8.7.0

Compare Source

Minor Changes
  • 4914970: mergeSchemas was skipping defaultFieldResolver and defaultMergedResolver by default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So new includeDefaultMergedResolver flag is introduced in getResolversFromSchema to put default "proxy" resolvers in the extracted resolver map for mergeSchemas.

    This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing defaultMergedResolver in the final merged schema which should come from the wrapped schema.

v8.6.13

Compare Source

Patch Changes
  • 041c5ba: Use caret range for the tslib dependency

v8.6.12

Compare Source

Patch Changes
  • da7ad43: Fix GraphQL v17 incompatibility issues and introduce createGraphQLError helper function for backwards compatibility.

v8.6.11

Compare Source

Patch Changes

v8.6.10

Compare Source

Patch Changes
  • 0fc510c: Interface implementations should be included when a return type is an interface.

v8.6.9

Compare Source

Patch Changes
  • 31a33e2: pruneSchema will no longer removed used input object type.

v8.6.8

Compare Source

Patch Changes
  • cb23887: pruneSchema will now prune unused implementations of interfaces

v8.6.7

Compare Source

Patch Changes
  • 0bbb176: Refine generic typings using extends X when appropriate

    Typescript 4.7 has stricter requirements around generics
    which is explained well in the related https://github.com/microsoft/TypeScript/pull/48366ll/48366

    These changes resolve the errors that these packages will
    face when attempting to upgrade to TS 4.7 (still in beta
    at the time of writing this). Landing these changes now
    will allow other TS libraries which depend on these
    packages to experiment with TS 4.7 in the meantime.

v8.6.6

Compare Source

Patch Changes
  • 904c084: Support deprecated directive on enum values

v8.6.5

Compare Source

Patch Changes
  • be2c02d: fix(utils): use 3 as inspect recursive depth

v8.6.4

Compare Source

Patch Changes
  • d36d530: fix(utils): pass the value as-is if it cannot be parsed by the actual type

v8.6.3

Compare Source

Patch Changes

v8.6.2

Compare Source

Patch Changes
  • 1834136: feat(visitResult): ignore if field not present in visited object

v8.6.1

Compare Source

Patch Changes
  • 041c5ba: Use caret range for the tslib dependency

v8.6.0

Compare Source

Minor Changes
  • 69b316c: feat(utils): more withCancel utils

v8.5.5

Compare Source

Patch Changes
  • 7b5d72c: enhance(utils): better typing for withCancel

v8.5.4

Compare Source

Patch Changes
  • 5131561: enhance: avoid using globalThis

v8.5.3

Compare Source

Patch Changes
  • 960e178: fix: isAsyncIterable should check if it is an object with iterator factory function
  • 947a3fe: enhance(utils): show error with details in inspect fn

v8.5.2

Compare Source

Patch Changes
  • 233e037: fix(utils): respect new specifiedByURL of GraphQL v16

v8.5.1

Compare Source

Patch Changes
  • 4bfb342: enhance: use ^ for tslib dependency

v8.5.0

Compare Source

Minor Changes
  • ad04dc7: enhance: make operationType optional

v8.4.0

Compare Source

Minor Changes
  • 149afdd: fix: getting ready for GraphQL v16

v8.3.0

Compare Source

Minor Changes
  • 58262be: feat(utils): export createDefaultRules

v8.2.5

Compare Source

Patch Changes
  • 1043219: fix implicit dependencies

v8.2.4

Compare Source

Patch Changes
  • 014937d: batch-execute enhancements:
    • fixes bugs with batched fragment definitions
    • unpathed errors are now returned for all batch results
    • the "graphqlTools" prefix is simplified down to just "_"
    • new tests and documentation

v8.2.3

Compare Source

Patch Changes
  • da157d6: fix(utils): Avoid processing read-only properties on visitData method

v8.2.2

Compare Source

Patch Changes
  • d4918a7: fix(commentDescriptions): handle descriptions and comments correctly during merge

v8.2.1

Compare Source

Patch Changes
  • 50609df: fix(utils): print specifiedBy directive correctly
  • be6fdb8: fix(utils): bring back breaking change for fixSchemaAst

v8.2.0

Compare Source

Minor Changes
  • c5b0719: enhance(utils): copy inspect util from graphql-js
  • c5b0719: feat: GraphQL v16 support
  • c5b0719: enhance(utils): move memoize functions to utils
  • c5b0719: enhance(utils): copy collectFields from graphql-js@16 for backwards compat
Patch Changes
  • c5b0719: enhance(utils): memoize root types utility functions

v8.1.2

Compare Source

Patch Changes
  • c8c13ed: enhance: remove TypeMap and small improvements

v8.1.1

Compare Source

Patch Changes
  • 2c807dd: enhance(buildOperationNodeForField): mutation response return a field of type Query

v8.1.0

Compare Source

Minor Changes
  • b968463: feat(validate-documents): more clear error messages with stack

  • 67691b7: - schemaExtensions option has been added to mergeSchemas, makeExecutableSchema and stitchSchemas configurations

    Breaking Changes;

    • Move mergeSchemas and MergeSchemasConfig from @graphql-tools/merge to @graphql-tools/schema package to prevent circular dependency between them.
    • mergeSchemasAsync has been removed.
    • Move NamedDefinitionNode, resetComments, collectComment, pushComment and printComment from @graphql-tools/merge to @graphql-tools/utils.
Patch Changes
  • 9ede806: enhance(utils): use inspect from graphql-js instead of node:util #​3324

v8.0.2

Compare Source

Patch Changes
  • 0483004: fix(utils): support old TypeScript versions

v8.0.1

Compare Source

Patch Changes
  • b823dba: fix(utils): fix AggregateErrorConstructor type issue

v8.0.0

Compare Source

Major Changes
  • af9a78d: BREAKING CHANGE

    • Now each loader handles glob patterns internally and returns an array of Source object instead of single Source

    • GraphQL Tag Pluck now respects code locations and returns graphql-js Source objects for each found code block

    • Thanks to the one above, CodeFileLoader now returns different Source objects for each found SDL code block.

  • 7d3e300: BREAKING CHANGE

    • Remove fieldToFieldConfig, argsToFieldConfigArgument and argumentToArgumentConfig
      • You can use .toConfig method instead for each.
  • 7d3e300: BREAKING CHANGE

  • dae6dc7: refactor: ExecutionParams type replaced by Request type

    rootValue property is now a part of the Request type.

    When delegating with delegateToSchema, rootValue can be set multiple ways:

    • when using a custom executor, the custom executor can utilize a rootValue in whichever custom way it specifies.
    • when using the default executor (execute/subscribe from graphql-js):
      -- rootValue can be passed to delegateToSchema via a named option
      -- rootValue can be included within a subschemaConfig
      -- otherwise, rootValue is inferred from the originating schema

    When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.

  • 6877b91: BREAKING CHANGES;

    mergeDeep now takes an array of sources instead of set of parameters as input and it takes an additional flag to enable prototype merging
    Instead of mergeDeep(...sources) => mergeDeep(sources)

  • c42e811: BREAKING CHANGES;

    • Rename Request to ExecutionRequest
    • Add required operationType: OperationTypeNode field in ExecutionRequest
    • Add context in createRequest and createRequestInfo instead of delegateToSchema

    It doesn't rely on info.operation.operationType to allow the user to call an operation from different root type.
    And it doesn't call getOperationAST again and again to get operation type from the document/operation because we have it in Request and ExecutionPhttps://github.com/ardatan/graphql-tools/pull/3166ls/pull/3166/files#diff-d4824895ea613dcc1f710c3ac82e952fe0ca12391b671f70d9f2d90d5656fdceR38

    Improvements;

    • Memoize defaultExecutor for a single GraphQLSchema so allow getBatchingExecutor to memoize batchingExecutor correctly.
    • And there is no different defaultExecutor is created for subscription and other operation types. Only one executor is used.

    Batch executor is memoized by executor reference but createDefaultExecutor didn't memoize the default executor so this memoization wasn't working correctly on batch-execute side.
    https://github.com/ardatan/graphql-tools/blob/remove-info-executor/packages/batch-execute/src/getBatchingExecutor.ts#L9

  • 7d3e300: BREAKING CHANGE

    • Now it uses the native AggregateError implementation. The major difference is the individual errors are kept under errors property instead of the object itself with Symbol.iterator.
    // From;
    for (const error of aggregateError)
    // To;
    for (const error of aggregateError.errors)
  • 8c8d4fc: BREAKING CHANGE: remove cloneSchema

  • 7d3e300: BREAKING CHANGE

    • No longer exports debugLog but uses console.log directly only if DEBUG is available under process.env
  • 7d3e300: BREAKING CHANGE

    • No longer applies camelCase naming convention in buildOperationNodeForField
  • 74581cf: fix(getDirectives): preserve order around repeatable directives

    BREAKING CHANGE: getDirectives now always return an array of individual DirectiveAnnotation objects consisting of name and args properties.

    New useful function getDirective returns an array of objects representing any args for each use of a single directive (returning the empty object {} when a directive is used without arguments).

    Note: The getDirective function returns an array even when the specified directive is non-repeatable. This is because one use of this function is to throw an error if more than one directive annotation is used for a non repeatable directive!

    When specifying directives in extensions, one can use either the old or new format.

  • c0ca319: BREAKING CHANGE

    • Remove Subscriber and use only Executor
      • Now Executor can receive AsyncIterable and subscriptions will also be handled by Executor. This is a future-proof change for defer, stream and live queries
  • 7d3e300: BREAKING CHANGE

    • No longer exports SchemaVisitor, visitSchema and VisitSchemaKind
Minor Changes
  • 9c26b84: enhance(loaders): remove optional methods from the Loader interface
  • 7d3e300: feat(utils): Respect operationName and rootValue in ExecutionParams
Patch Changes
  • 982c8f5: enhance(utils): refactor, cleanup and remove extra work

v7.10.0

Compare Source

Minor Changes
  • e632c5d: Make executors not generic over context types
Patch Changes
  • 99f092f: fix(getResolversFromSchema) Fix resolvers for type names starting with a single underscore.

v7.9.1

Compare Source

Patch Changes
  • be23817: enhance(utils): do not extract default resolvers

v7.9.0

Compare Source

Minor Changes
  • 20d2c7b: feat(utils): add withCancel

v7.8.1

Compare Source

Patch Changes
  • dbdb78e: fix(visitResult): don't throw on encountering __typename in request (#​2860)

v7.8.0

Compare Source

Minor Changes
  • 03c579b: enhance(utils): astFromDirective doesn't need schema anymore

v7.7.3

Compare Source

Patch Changes
  • d2a17c7: enhance(printSchemaWithDirectives): show directives before other definitions #​2752

v7.7.2

Compare Source

Patch Changes
  • a4f1ee5: __ is reserved for introspection

v7.7.1

Compare Source

Patch Changes
  • 194ac37: fix(utils): add createSchemaDefinition again to fix breaking change

v7.7.0

Compare Source

Minor Changes
  • 58fd4b2: feat(types): add TContext to stitchSchemas and executor
Patch Changes
  • 43da6b5: enhance(merge): reduce number of iterations

v7.6.0

Compare Source

Minor Changes
  • 5b637e2: Add generic pruning filter option

v7.5.2

Compare Source

Patch Changes
  • de16fff: Fix pruneSchema with unimplemented interfaces

v7.5.1

Compare Source

Patch Changes
  • 33d1b9e: Fix pruneSchema with unused interfaces

v7.5.0

Minor Changes
  • 219ed39: enhance(utils): Extract getDocumentNodeFromSchema from printSchemaWithDirectives
Patch Changes
  • 219ed39: fix(utils): fix missing default value of input object type field
  • 219ed39: fix(utils): print specifiedBy directive definitions correctly

v7.4.0

Minor Changes
  • 8f331aa: enhance(utils): Extract getDocumentNodeFromSchema from printSchemaWithDirectives
Patch Changes
  • 8f331aa: fix(utils): fix missing default value of input object type field

v7.3.0

Compare Source

Minor Changes
  • 6387572: feat(utils): export astFrom* helper functions

v7.2.6

Compare Source

Patch Changes
  • e53f97b: fix(utils): provide { done: true } from iterator when complete is called on observer in observableToAsyncIterable

v7.2.5

Compare Source

Patch Changes
  • 4fc05eb: Fixes the handling of repeatable directives in the getDirectives method. Previously repeatable directives were nested and duplicated. They will now return as a flat array map:

    @​mydir(arg: "first") @​mydir(arg: "second")

    translates into:

    {
      mydir: [{ arg: 'first' }, { arg: 'second' }];
    }

v7.2.4

Compare Source

Patch Changes
  • 6e50d9f: enhance(stitching-directives): use keyField

    When using simple keys, i.e. when using the keyField argument to @merge, the keyField can be added implicitly to the types's key. In most cases, therefore, @key should not be required at all.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 803bc86 to 1c0abdf Compare March 7, 2022 08:54
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 1c0abdf to 61a12a5 Compare March 26, 2022 13:05
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 61a12a5 to 42db2b8 Compare April 24, 2022 23:23
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 42db2b8 to c0d09a6 Compare May 16, 2022 01:44
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 58947d4 to 3e6203c Compare June 23, 2022 19:28
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 3e6203c to 99dcaa9 Compare September 25, 2022 11:02
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 99dcaa9 to af66f6e Compare November 20, 2022 14:13
@renovate renovate bot changed the title fix(deps): update dependency @graphql-tools/utils to v8 fix(deps): update dependency @graphql-tools/utils to v9 Nov 20, 2022
@vladyslav-n
Copy link

vladyslav-n commented Jan 19, 2023

Hi
I guess, it's not possible to just update deps here: @graphql-tools/utils v.9 doesn't provide SchemaDirectiveVisitor class which is imported in src/directives/schemaDirectiveVisitors.ts
nestjs/nest#8481 (comment)

@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from af66f6e to 001a361 Compare March 16, 2023 20:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant